Client/server authentication over fibre channel

ABSTRACT

An authentication service to authenticate access requests over a Fibre Channel (FC) network is provided. An authentication request is generated by a client and is sent over the FC network to a server. The request can be a native FC message, such as a CT message. For example, authentication software can generate the native FC message. In another example, authentication software can send a UDP or TCP authentication request, and an application program interface (API) can translate the request into a native FC message, such as a CT message, and send the message over the FC network. In another example, the authentication request can be sent as an encapsulated IP over FC message. For example, an authentication client can communicate using UDP or TCP messages, and an HBA can encapsulate the messages as IP over FC and send the encapsulated messages over the FC network.

FIELD OF THE INVENTION

This relates generally to the authentication of network devices, and more particularly, to client/server authentication over a Fibre Channel (FC) network.

BACKGROUND OF THE INVENTION

An ever-increasing amount of data and services are being made available for access over distributed systems, such as computer networks. Storage area networks (SANs) are one example of distributed data storage network. A typical SAN includes multiple storage devices and servers or hosts that are networked together to provide a corresponding increase in the amount of storage available to the hosts. The storage devices in a typical SAN can be networked together using a variety of networking technologies. For example, Fibre Channel (FC) is one networking technology used in SANs.

One drawback of networked data storage systems, such as SANs, is that they can be vulnerable to unauthorized access, for example, break-ins by hackers. For this reason, many SANs include an authentication system that prevents a user from accessing a storage device in the SAN until the authentication system authenticates the user's identity and determines that the user is authorized to access the SAN. For example, the requesting device sends a name/password combination to the SAN, and the SAN's authentication process checks the name/password against a list of authorized name/password combinations. In another example, the requesting device sends a cryptographically hashed code to the SAN, and the authentication process runs the same algorithm to determine the authenticity and the authorization of the user.

Authentication servers in SAN's can authenticate devices as described in the prior paragraph. They also can typically be used as a way to authenticate users who login into devices in a network, in this case a SAN.

SUMMARY OF THE INVENTION

In view of the foregoing, an authentication service to authenticate access request messages over a Fibre Channel network is provided. An authentication request message for the authentication service is generated by a client device, and the authentication request message is sent over an FC network to a server. The authentication request message can be, for example, a native FC message such as a CT message. In this case, for example, an authentication client software can generate the native FC message to send to the server. In another example, an authentication client software can send a UDP or TCP authentication request message, and a driver application program interface (API) can translate the UDP or TCP message into a native FC message, such as a CT message, and send the native FC message over the FC network. The authentication request message can be sent, for example, as an encapsulated IP over FC message. In this case, for example, an authentication client software can generate and send a UDP or TCP authentication request message, and an HBA can encapsulate the UDP or TCP message as IP over FC and send the encapsulated message over the FC network.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example storage area network (SAN) with an authentication system.

FIG. 2 illustrates an example flow of authentication messages in the SAN of FIG. 1.

FIG. 3 illustrates an example SAN with an authentication system according to embodiments of the invention.

FIG. 4 illustrates an example authentication process according to embodiments of the invention.

FIG. 5 illustrates an example network stack according to embodiments of the invention.

FIG. 6 illustrates an example flow of authentication messages according to embodiments of the invention.

FIG. 7 illustrates another example SAN with an authentication system according to embodiments of the invention.

FIG. 8 illustrates another example authentication process according to embodiments of the invention.

FIG. 9 illustrates another example network stack according to embodiments of the invention.

FIG. 10 illustrates another example flow of authentication as it traverses the storage network stack according to embodiments of the invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

In the following description of preferred embodiments, reference is made to the accompanying drawings which form a part hereof, and in which it is shown by way of illustration specific embodiments in which the invention can be practiced. It is to be understood that other embodiments can be used and structural changes can be made without departing from the scope of the embodiments of this invention.

Although embodiments of the invention may be described and illustrated herein in terms of SANs, it should be understood that embodiments of this invention are not so limited, but are additionally applicable to other network environments, such as application server systems, wireless communication networks, corporate intra-networks, etc. Furthermore, although embodiments of the invention may be described and illustrated herein in terms of networks using FC switches solely or Fiber Channel switches implemented in a Fibre Channel over Ethernet (FCoE) environment, it should be understood that embodiments of the invention are also applicable to other system configurations and protocols, such as SAS, SATA, Infiniband, which may require porting to the corresponding technology.

FIG. 1 illustrates an example SAN 100 that includes an authentication system. A requesting computer 101 is linked to a storage device 103 through a Fibre Channel fabric of FC switches 105 a-b and FC connections 107 a-c. A Host Bus Adapter (HBA) 102 a in requesting computer 101 and an HBA 104 a in storage device 103 provide interfaces to the FC fabric. Requesting computer 101 could be any computing device that accesses stored data, for example, a personal computer, a peripheral device, a server, a portable computing device, etc. Likewise, storage device 103 could be any type of storage device capable of use in SAN 100, including a hard drive, a tape drive, an optical disk drive, a solid state memory device, virtual storage device, or other device or a plurality of devices such as a JBOD Oust a bunch of disks), a Redundant Array of Independent Disks (RAID) array, a jukebox of optical disks, etc.

FIG. 1 also shows requesting computer 101, storage device 103, authentication server 109, and FC switches 105 a-b connected to an Internet protocol (IP) management network 113 through IP connections 111 a-e. Network interface cards (NICs), such as NIC 102 b in requesting computer 101, NIC 104 b in storage device 103, and NIC 117 in authentication server 109, provide interfaces to IP management network 113. Authentication server 109 could be any device capable of supporting an authentication function of SAN 100, including a Remote Authentication Dial In User Service (RADIUS) server, a Terminal Access Controller Access-Control System Plus (TACACS+) server, a DIAMETER server, etc. While a plurality of requesting computers, storage devices, etc. could be linked together through the FC fabric, FIG. 1 shows a single requesting computer and storage device for the sake of clarity. Likewise, the IP management network could link together a plurality of clients, storage devices, and authentication servers, although for clarity only one of each is illustrated in FIG. 1.

In the example SAN illustrated in FIG. 1, requesting computer 101 requests access to storage device 103 by sending an access request message to storage device 103 through the FC fabric, that is, through FC connections 107 a-c and FC switches 105 a-b. For example, the access request message could include a request to send a file stored in storage device 103 to requesting computer 101. The access request message may include the requestor's name that is subsequently authenticated to ensure proper authorization for access to the requested data, e.g., the requested file. Prior to sending the requested file to requesting computer 101, the name of the entity issuing the access request is authenticated using authentication server 109. In particular, storage device 103 sends an authentication request message to authentication server 109. The authentication request message includes the authentication data from the access request message (e.g. challenge message), which is processed by authentication server software application 115 to determine the authentication of the access request message sender.

In the example system of FIG. 1, storage device 103 sends the authentication request message to authentication server 109 through IP management network 113, that is, through IP connections 111 b and 111 c, and IP management network 113. The authentication request message is received by NIC 117 of authentication server 109, which processes the message via a standard IP stack, e.g., stripping away IP headers/routing headers, and sends the authentication request data up the stack to be processed by authentication server software application 115. After processing the authentication request, authentication server 109 sends a reply message (such as a pass/fail message) via IP protocols to storage device 103.

FIG. 1 shows an example of an authentication process that could be used. Storage device 103 might alternatively skip this authentication process for the sender of the access request by, for example, sending the requested file or data to requesting computer 101 without authenticating. On the other hand, storage device 103 might decide to authenticate requesting computer 101, as shown, prior to sending the file. In general, a decision whether to authenticate can be dependent on, for example, the connection between one device and another. For example, a system with clients A to Z and storage devices 1 to 20 might be set up so that communications between A and 5, B and 5, B and 7, D and 20, etc . . . require authentication, but other connections do not.

FIG. 2 illustrates an authentication process that can occur after storage device 103 receives such an access request message from requesting computer 101. As shown in the example of FIG. 2, storage device 103 sends a challenge message 201 to requesting computer 101 over the FC fabric, and the requesting computer replies with a reply message 203 over the FC fabric. The reply message includes authentication data of requesting computer 101.

It is noted that one way to handle authentication (not shown in FIG. 2) is by processing a reply message locally. That is, authentication can be handled without an authentication server by processing the authentication data in the reply message locally, e.g., storage device 103 runs an authentication application locally to verify the reply message from requesting computer 101. This would potentially require each SAN device to have locally installed authentication software and to use local processor time with verification processing. In addition, in the case that the authentication scheme utilizes individual authentication keys (such as passwords), each SAN device could potentially be required to handle many keys (e.g., a pair of keys, one for each direction in bi-directional authentication for each connection the device has with another device). Such an authentication process for an FC SAN typically is handled via a Challenge-Handshake Authentication Protocol (CHAP), such as DH-CHAP (Diffie-Hellman CHAP).

Referring again to FIG. 2, storage device 103 sends the authentication data encapsulated in an IP authentication request message 205 over IP management network 113. Similar to the example of FIG. 1, authentication server 109 receives authentication request message 205 and processes the authentication data through authentication server software application 115. Authentication server 109 generates and transmits a pass/fail message 207 to storage device 103 over IP management network 113. If requesting computer 101 is authenticated (i.e., message 207 indicates “pass”), then storage device 203 sends the requested file/data.

FIG. 3 illustrates an example SAN 300 including an authentication system according to embodiments of the invention. SAN 300 includes a requesting computer 301 with an authentication client application software 302 b, a driver application program interface (API) 302 c, a user interface 302 d, a storage medium 302 e, and an HBA 302 a linked to a storage device 303 with an authentication client application software 304 b, a driver API 304 c, a storage medium 304 e, and an HBA 304 a through a Fibre Channel fabric including FC switches 305 a-b and FC connections 307 a-c. SAN 300 also includes an authentication server 309 that includes an authentication server software application 315. Unlike the system of FIG. 1, authentication server 309 is linked to the FC fabric through an FC connection 307 d. Specifically, authentication server 309 includes an HBA 311 that is connected to FC connection 307 d, which is connected to FC switch 305 a. Authentication server 309 also includes an FC HBA driver 313, a driver API 317 to interface to authentication server software application 315, and a storage medium 319. Storage media 302 e, 304 e, and 319 store computer-executable program instructions that are executed to perform the processes described herein. The storage media can be, for example, computer memory, disk drives, optical memory, etc.

SAN 300 allows authentication communications using Fibre Channel. In this example system, a new set of native FC messages can be created and utilized for the authentication communications.

In other words, client/server authentication messages/commands can be implemented in CT (Common Transport) layer of Fibre Channel sent over the Fibre Channel fabric using FC layer 2 protocols. APIs 302 c, 304 c and 317 can provide an interface for those applications that do not communicate using native FC messages. For example, authentication client application software 302 b and 304 b and authentication server application software 315, which can communicate using UDP or TCP, can call a respective API to translate to/from native FC messages. In this case, some native FC messages can be created that correspond to authentication messages in UDP or TCP, such as conventional IP authentication messages such as those defined in RADIUS.

In some cases, other native FC authentication messages can be created that provide additional functionality and benefits over conventional authentication messages using UDP. For example, authentication client/server application software that communicates via native FC messages can be created. Authentication services offered by this software could take advantage of the full range of authentication services included with Fibre Channel. In the present embodiment, user interface 302 d can be a graphical user interface (GUI) capable of communication using native FC messages, such as HBAnyware™ of Emulex SAN management software, which can provide tools to interface with HBA 304 a of storage device 303, allowing a user to access and manage FC functions of HBA 304 a. In this example, user interface 302 d can configure the use of the new set of native FC messages created for the authentication communications. The username of the person using the user interface of SAN devices may also be authenticated using the new messages between the authentication client/server. User interface 302 d is a stand-alone software program in the present example, but in other embodiments user interface 302 d might be included in or bundled with another software program, such as authentication client application software 304 b. Authentication client application software 304 b of storage device 303 can operate independently of and/or in conjunction with user interface 302 d to manage authentication functions of storage device 303. That is, the user interface, for example, could force an authentication of the device to occur. Both user interface 302 d and authentication client application software 304 b can send/receive messages through HBA 304 a.

FIG. 4 illustrates an example authentication process according to embodiments of the invention. Requesting computer 301 requests access to storage device 303 by sending a negotiation message 405 to the storage device. After receiving negotiation message 405, authentication client software 304 b sends an authentication challenge 407 to requesting computer 301. HBA 304 a sends authentication challenge 407 as a lower layer standard FC message to requesting computer 301. Requesting computer 301 replies with a reply message 411. Upon receipt, reply message 411 is routed appropriately (e.g., to authentication client application software 304 b). Authentication client software 304 b initiates an authentication process using native FC messages. In particular, after receiving reply message 411, which includes authentication data of requesting computer 301 (such as hash of authentication key and other identity information), storage device 303 sends an authentication request message 413 to authentication server 309 as a Fibre Channel CT message through the Fibre Channel fabric, FC layer 2.

More specifically, authentication client software 304 b sends authentication request message 413 as a UDP or TCP message, which is converted by driver API 304 c into a CT message. The CT message is processed by HBA 304 a and sent over FC layer 2 to authentication server 309. As described in more detail below with reference to FIGS. 5 and 6, the CT authentication request message 413, and other native FC-based messages and commands sent to authentication server 309, are processed by HBA 304 a down a network stack for transporting authentication client/server messages over the Fibre Channel fabric.

Authentication server 309 receives request message 413 and processes the request message up a network stack of HBA 311 from FC layer 2 to a FC CT layer and sends the request message to driver API 317. Driver API 317 converts the message into a UDP or TCP message, which is sent to authentication server application software 315. Application software 315 processes request message 413 and sends a reply message 419, e.g. indicating a pass or a fail, in UDP or TCP to driver API 317. Driver API 317 converts the UDP or TCP reply message into a CT reply message, and sends the CT reply message to HBA 311. HBA 311 processes CT reply message 419 down the network stack to FC CT layer and then FC layer 2 and sends the reply message to storage device 303 through the FC fabric. Storage device 303 receives and processes reply message 419 through the network stack of HBA 304 a and sends CT reply message 419 to driver API 304 c. Driver 304 c converts CT reply message 419 into a UDP or TCP reply message 419 and sends the reply message to authentication client software 304 b, which determines whether to send the requested file/data to requesting computer 301 based on the pass/fail indicated by reply message 419. Authentication client software 304 b sends a grant/deny message 421 to requesting computer 301. For example, if reply message 419 indicated “pass”, the message 421 can be the file/data that computer 301 requested. If reply message 419 indicated “fail”, message 421 can indicate that requesting computer 301 has failed authentication.

FIG. 5 shows an example network stack 500 according to embodiments of the invention. The network stacks of HBA 304 a and HBA 311 could be, for example, each implemented as a network stack 500. Network stack 500 includes a layer 501 for converting FC authentication client/server messages in CT protocol into Transmission Control Protocol (TCP) or User Datagram Protocol (UDP) Stack 500 also includes layer 503 for layer 3 processing of FC authentication client/server messages and a layer 505 for processing messages in FC layer 2.

Network stack 500 allows storage device 303 and authentication server 309 to communicate over the FC fabric using native FC messages. In particular, new FC authentication client/server messages can be created to implement a variety of authentication functions. Some FC authentication client/server messages could, for example, implement functions similar to conventional authentication command messages, e.g., RADIUS server commands, such as authentication request messages, pass/fail messages, etc. On the other hand, some FC authentication client/server messages could implement new functionality. Because FC authentication client/server messages utilize FC, network stack 500 can implement additional services beyond those available in conventional IP server authentication, such as those defined in RADIUS. In other words, many authentication services that are already supported by FC can be tapped into by new FC authentication client/server messages that are sent and received through network stacks such as network stack 500 in, for example, storage device 303 and authentication server 309 of example SAN 300.

FIG. 6 shows an example flow of authentication messages according to embodiments of the invention. A device 601, such as a switch, storage device, etc., processing an authentication request message in a ULP, such as CT protocol, sends an authentication request message 603 to a device 605, such as an HBA, switch, etc. Device 605 processes request message 603 into FC layer 2, and sends the request message as FC frames 607 to a device 609. Device 609 is, for example, another HBA, switch, etc. of an authentication server. Device 609 processes FC frames 607 into an authentication request message 611, and sends the request message to be processed in a ULP process 613, such as CT protocol. ULP process 613 sends the request message 615 to an FC to UDP converter 617, which converts the request message to UDP as request message 619 and sends request message 619 to be processed by authentication server application software 621. Software 621 generates and sends a reply message 623, which is in UDP format. Reply message 623 is converted by device 617 into CT protocol, and the reply message is sent back to device 601 through processing similar to the foregoing.

FIG. 7 illustrates another example SAN 700 including an authentication system according to embodiments of the invention. Similar to the system of FIG. 3, SAN 700 includes a requesting computer 701 with an authentication client application software 702 b, user interface 702 d, a storage medium 702 e, and an HBA 702 a linked to a storage device 703 with an authentication client application software 704 b, user interface 704 d, a storage medium 704 e, and an HBA 704 a through a Fibre Channel fabric including FC switches 705 a-b and FC connections 707 a-c. SAN 700 also includes an authentication server 709 that includes an authentication server software application 715. Authentication server 709 is linked to the FC fabric through an FC connection 707 d. Specifically, authentication server 709 includes an HBA 711 that is connected to FC connection 707 d, which is connected to FC switch 705 a. Authentication server 709 also includes an FC HBA driver 713 and storage medium 719. Storage media 702 e, 704 e, and 719 store computer-executable program instructions that are executed to perform the processes described herein. The storage media can be, for example, computer memory, disk drives, optical memory, etc

In contrast to the example system of FIG. 3, SAN 700 allows authentication communications over the Fibre Channel fabric while utilizing UDP or TCP messages more directly (e.g., without native FC authentication messages). For example, authentication messages/commands in UDP or TCP protocol can be encapsulated within FC messages, such as IPv6 or IPv4 over FC messages. In this example, the HBAs process messages using a network stack, described in more detail below with respect to FIG. 9, to encapsulate/decapsulate UDP or TCP authentication messages when an HBA communicates with a user interface and/or an authentication client/server application software. Thus, unlike the system of FIG. 3, requesting computer 701, storage device 703, and authentication server 709 do not include application program interfaces because there is no need to translate between UDP or TCP messages and native FC authentication messages.

FIG. 8 illustrates an example authentication process according to embodiments of the invention. Requesting computer 701 requests access to storage device 703 by sending a negotiation message 805 to the storage device. After receiving negotiation message 805, authentication client software 704 b sends an authentication challenge 807 to requesting computer 701. HBA 704 a sends authentication challenge 807 as a lower layer standard FC message to requesting computer 701. Requesting computer 701 replies with a reply message 811. Upon receipt, reply message 811 is routed appropriately (e.g., to authentication client application software 704 b). Authentication client software 704 b initiates an authentication process using UDP or TCP messages. In particular, after receiving reply message 811, which includes authentication data of requesting computer 701 (such as hash of authentication key and other identity information), storage device 703 sends an authentication request message 813 to authentication server 709 as a UDP or TCP message, which is encapsulated as IP over FC and transmitted through the Fibre Channel fabric, FC layer 2.

More specifically, after receiving an access request message from requesting computer 701, authentication client software 704 b sends a UDP or TCP request message 813 to HBA 704 a. HBA 704 a encapsulates UDP or TCP request 813 as an IP over FC message, which is transmitted to authentication server 709 as a Fibre Channel layer 2 message. Authentication server 709 receives request message 813 and processes the request message via HBA 711 to decapsulate the UDP or TCP request message 813, which is sent to authentication server software 715. Authentication server software 715 processes request message 813 and sends a UDP or TCP reply message 819, e.g. indicating a pass or a fail, to HBA 711. HBA 711 processes the reply message to encapsulate the UDP or TCP message as an IP over FC message, which is transmitted to storage device 703 over FC layer 2 through the FC fabric. Storage device 703 receives and decapsulates UDP or TCP reply message 819 through the network stack of HBA 704 a, and sends the UDP or TCP reply message to authentication client software 704 b, which determines whether to send the requested file/data to requesting computer 701 based on the pass/fail indicated by reply message 819. Authentication client software 704 b sends a grant/deny message 821 to requesting computer 701. For example, if reply message 819 indicated “pass”, the message 821 can be the file/data that computer 701 requested. If reply message 819 indicated “fail”, message 821 can indicate that requesting computer 701 has failed authentication.

FIG. 9 shows an example network stack 900 according to embodiments of the invention. The network stacks of HBA 704 a and HBA 711 could be, for example, each implemented as a network stack 900. Network stack 900 includes a layer 901 for encapsulating authentication client/server messages in UDP or TCP protocol as IPv6 or IPv4 over FC messages. Stack 900 also includes layer 903 for layer 3 processing of encapsulated authentication client/server messages and a layer 905 for processing messages in FC layer 2.

Network stack 900 allows storage device 703 and authentication server 709 to communicate UDP or TCP messages over the FC fabric using encapsulation. Utilizing network stacks 900 in SAN 700, for example, can allow conventional UDP or TCP authentication commands to be used, while at the same time potentially gaining benefits of increased reliability and faster boot up of Fibre Channel.

FIG. 10 shows another example flow of authentication messages according to embodiments of the invention. A device 1001, such as a switch, storage device, etc., processing an authentication request message in a ULP, such as UDP or TCP protocol, sends the authentication request message 1003 to a device 1009, such as an HBA, switch, etc. Device 1009 encapsulates the UDP or TCP request message 1003 into IP over FC as an encapsulated message 1011 and sends the encapsulated message via FC layer 2 to a device 1013. Device 1013 is, for example, another HBA, switch, etc. of an authentication server. Device 1013 processes encapsulated message 1011 to decapsulate the message to a UDP or TCP authentication request message 1015, and sends the request message to be processed by authentication server application software 1021. Software 1021 generates and sends a reply message 1023, which is in UDP format. Reply message 1023 is encapsulated into IP over FC by device 1013, and the encapsulated reply message is sent back to device 1001 through processing similar to the foregoing.

The foregoing example embodiments, and other embodiments, can potentially provide many advantages over conventional systems. For example, using Fibre Channel as the transport layer for authentication communications can be more reliable than utilizing IP communications for authentication purposes. In addition, failover systems could be implemented within a single authentication server, for example, by providing the server with multiple HBAs that have authentication capability. This may also reduce the complexity of a cascaded or chained authentication system, which could potentially allow for quicker setup and maintenance procedures.

In addition, as discussed above, Fibre Channel's fast availability at boot up may be exploited in an authentication system. This would increase the availability of the authentication system, and could reduce or eliminate the wait time between when a Fibre Channel device is available after bootup and when authentication services are available after the bootup. For example, many conventional SANs that utilize Fibre Channel for data transfer/communication cannot take advantage of Fibre Channel's fast bootup because, even though the Fibre Channel devices are ready to be accessed quickly after bootup, the conventional authentication services for the storage area network are not available until the IP stack is fully initialized. Therefore, the Fibre Channel devices in many conventional SANs must wait for authentication services through traditional RADIUS server to become available before allowing access.

Although embodiments of this invention have been fully described with reference to the accompanying drawings, it is to be noted that various changes and modifications will become apparent to those skilled in the art. Such changes and modifications are to be understood as being included within the scope of embodiments of this invention as defined by the appended claims. For example, although authentication services are provided in the above example embodiments by a dedicated authentication server, authentication services could be provided by incorporating some or all of the foregoing authentication server functions into one or more Fibre Channel fabric switches. 

1. A method for providing an authentication service to authenticate access request messages, comprising: generating, by a client device, an authentication request message for the authentication service; sending the authentication request message for the authentication service from the client device over a Fibre Channel (FC) network; receiving the authentication request message at a server device that provides the authentication service; generating, by the server device, a reply message to the authentication request message; sending the reply message from the server device over the FC network; and receiving the reply message at the client device, the reply message providing an indication of whether an access request message has been authenticated.
 2. A method for receiving an authentication service to authenticate access request messages comprising: generating, by a client device, an authentication request message for the authentication service; sending the authentication request message from the client device over a Fibre Channel (FC) network; and receiving a reply message in response to the authentication request message over the FC network, the reply message providing an indication of whether an access request message has been authenticated.
 3. The method of claim 2, wherein generating an authentication request message includes processing the authentication request message in an upper layer protocol (ULP) of FC, and sending the authentication request message includes processing the authentication request message from the ULP to a lower layer protocol (LLP) of FC.
 4. The method of claim 3, wherein the ULP is a common transport (CT) protocol of FC.
 5. The method of claim 3, wherein the LLP is FC layer
 2. 6. The method of claim 2, wherein generating an authentication request message includes translating the authentication request message from a non-FC protocol into an upper layer protocol (ULP) of FC.
 7. The method of claim 6, wherein the non-FC protocol is one of universal datagram protocol (UDP) and transmission control protocol (TCP).
 8. The method of claim 6, wherein the ULP is a common transport (CT) protocol of FC.
 9. The method of claim 2, wherein generating an authentication request message includes processing the authentication request message in a non-FC protocol, and sending the authentication request message includes encapsulating the authentication request message in an FC message.
 10. The method of claim 9, wherein the authentication request message is encapsulated as one of IPv6 over FC and IPv4 over FC.
 11. A method for providing an authentication service to authenticate access request messages comprising: receiving, by a server device that provides the authentication service, an authentication request message for the authentication service sent over a Fibre Channel (FC) network; generating, by the server device, a reply message to the authentication request message; and sending the reply message from the server device over the FC network.
 12. The method of claim 10, wherein receiving an authentication request message includes processing the authentication request message from a lower layer protocol (LLP) of FC to an upper layer protocol (ULP) of FC.
 13. The method of claim 12, wherein the ULP is a common transport (CT) protocol of FC.
 14. The method of claim 12, wherein the LLP is FC layer
 2. 15. The method of claim 11, wherein generating a reply message includes translating the reply message from a non-FC protocol into an upper layer protocol (ULP) of FC.
 16. The method of claim 15, wherein the non-FC protocol is one of universal datagram protocol (UDP) and transmission control protocol (TCP).
 17. The method of claim 15, wherein the ULP is a common transport (CT) protocol of FC.
 18. A system for providing an authentication service to authenticate access request messages comprising: a client device that generates and sends an authentication request message for the authentication service, and receives a reply message to the authentication request message; a server device that receives the authentication request message, and generates and sends the reply message to the authentication request message; and a Fibre Channel (FC) network that transports the authentication request message and the reply message.
 19. A client device in a system for providing an authentication service to authenticate access request messages comprising: a generator that generates an authentication request message for the authentication service; and an adapter that sends the authentication request message over a Fibre Channel (FC) network, and receives a reply message to the authentication request message over the FC network.
 20. The client device of claim 19, wherein the generator generates the authentication request message in a non-FC protocol, the client device further comprising: an application interface that translates the authentication request message from the non-FC protocol into an upper layer protocol (ULP) of FC.
 21. The method of claim 19, wherein the generator generates the authentication request message in a non-FC protocol, and sending the authentication request message by the adapter includes encapsulating the authentication request message in an FC message.
 22. The client device of claim 19, wherein sending the authentication request message by the adapter includes processing the authentication request message from an upper layer protocol (ULP) of FC to a lower layer protocol (LLP) of FC.
 23. A server device in a system for providing an authentication service to authenticate access request messages comprising: an adapter that receives an authentication request message for the authentication service over a Fibre Channel (FC) network, and sends a reply message to the authentication request message over the FC network; and a generator that generates the reply message.
 24. The server device of claim 23, wherein receiving an authentication request message by the adapter includes processing the authentication request message from a lower layer protocol (LLP) of FC to an upper layer protocol (ULP) of FC.
 25. The server device of claim 23, wherein generating a reply message by the generator includes translating the reply message from a non-FC protocol into an upper layer protocol (ULP) of FC.
 26. Computer-executable program instructions, stored on a computer-readable medium, for supporting an authentication service to authenticate access request messages, the program instructions executable to perform a method comprising: receiving an authentication request message for the authentication service, wherein the authentication request message is in an upper layer protocol (ULP) of FC; processing the authentication request message from the ULP to a lower layer protocol (LLP) of FC; and sending the authentication request message over a Fibre Channel (FC) network.
 27. The program instructions of claim 26, the program instructions incorporated in a network stack.
 28. The program instructions of claim 27, the network stack incorporated in a host bus adapter and associated software.
 29. Computer-executable program instructions, stored on a computer-readable medium, for supporting an authentication service to authenticate access request messages, the program instructions executable to perform a method comprising: receiving an authentication request message for the authentication service, wherein the authentication request message is in a non-FC protocol; processing the authentication request message by encapsulating the authentication request message in an FC message; and sending the authentication request message encapsulated in the FC message over a Fibre Channel (FC) network.
 30. The program instructions of claim 29, the program instructions incorporated in a network stack.
 31. The program instructions of claim 30, the network stack incorporated in a host bus adapter and associated software.
 32. Computer-executable program instructions, stored on a computer-readable medium, for supporting an authentication service to authenticate access request messages, the program instructions executable to perform a method comprising: receiving an authentication request message for the authentication service, wherein the authentication request message is in a non-FC protocol; processing the authentication request message by translating the authentication request message from the non-FC protocol into an upper layer protocol (ULP) of FC; and sending the authentication request message to be transmitted over a Fibre Channel (FC) network.
 33. The program instructions of claim 29, the program instructions incorporated in an application program interface. 